🤖 triggering CI on branch 'release-next' after synching from upstream/main #669
Conversation
serverless-qe
force-pushed
the
release-next-ci
branch
from
860bf33
to
c063b14
Compare
|
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: serverless-qe The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Codecov Report
❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more. @@ Coverage Diff @@
## release-next #669 +/- ##
================================================
+ Coverage 51.56% 53.50% +1.93%
================================================
Files 97 106 +9
Lines 13792 14378 +586
================================================
+ Hits 7112 7693 +581
+ Misses 6045 5987 -58
- Partials 635 698 +63
Flags with carried forward coverage won't be shown. Click here to find out more. |
|
OCF Webhook is merging this PR |
1 similar comment
|
OCF Webhook is merging this PR |
No description provided.